Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c811b4812e157ccf42eea0effd8ca90debff088938fec832bb7fc5bb3c693dec

Tx prefix hash: a83b5df26891e1c0146cc6a3ba8fc176f0b4477ec67603e3ebafd42606eb202a
Tx public key: 86851e2c3e27f4b5f7f6d626884c5581e1dad91279ce9a78fe624e8d2d000e95
Timestamp: 1762982981 Timestamp [UCT]: 2025-11-12 21:29:41 Age [y:d:h:m:s]: 00:040:14:42:39
Block: 1410776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29073 RingCT/type: yes/0
Extra: 0186851e2c3e27f4b5f7f6d626884c5581e1dad91279ce9a78fe624e8d2d000e95021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cae1affcc8d306bdde806b6b9eeeaa66fef9f9311afbfc67b64d935b35fa3786 0.600000000000 1899229 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1410786, "vin": [ { "gen": { "height": 1410776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cae1affcc8d306bdde806b6b9eeeaa66fef9f9311afbfc67b64d935b35fa3786" } } ], "extra": [ 1, 134, 133, 30, 44, 62, 39, 244, 181, 247, 246, 214, 38, 136, 76, 85, 129, 225, 218, 217, 18, 121, 206, 154, 120, 254, 98, 78, 141, 45, 0, 14, 149, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8