Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d7d1f2d0605be96dc55e695cb479d55c59622a23c6fff9f7713c0a94b68fd24

Tx prefix hash: ab8de7acc39c9c9ab27197a838e1306b931dd19be050e4c248262d37fd68e815
Tx public key: cc3bc9da656cc4c3b863b51d1699936d7310cc8c3a230d10a4825c11b04923f2
Timestamp: 1754421781 Timestamp [UCT]: 2025-08-05 19:23:01 Age [y:d:h:m:s]: 00:153:03:35:38
Block: 1340973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108538 RingCT/type: yes/0
Extra: 01cc3bc9da656cc4c3b863b51d1699936d7310cc8c3a230d10a4825c11b04923f20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 176cc086746dbaf5519f79dd53e170331e2d8fb19dcb80c4aee9e422919cfdf0 0.600000000000 1828794 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": 1340983, "vin": [ { "gen": { "height": 1340973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "176cc086746dbaf5519f79dd53e170331e2d8fb19dcb80c4aee9e422919cfdf0" } } ], "extra": [ 1, 204, 59, 201, 218, 101, 108, 196, 195, 184, 99, 181, 29, 22, 153, 147, 109, 115, 16, 204, 140, 58, 35, 13, 16, 164, 130, 92, 17, 176, 73, 35, 242, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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