Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5fcfc18190a94f3b24feb5d51b40be2c3594549067df56ddc8a488bcb66c5a7

Tx prefix hash: 1d1c897349dab4420ce880c45cf9ebbddd6f59948d60c8a0e244d9b142f87fd1
Tx public key: da2f07b3aa709248b8d1019b71b9aa868af37b59965c306a1b2ce5eedb8fcd19
Timestamp: 1763891642 Timestamp [UCT]: 2025-11-23 09:54:02 Age [y:d:h:m:s]: 00:004:21:31:20
Block: 1418306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3509 RingCT/type: yes/0
Extra: 01da2f07b3aa709248b8d1019b71b9aa868af37b59965c306a1b2ce5eedb8fcd190211000000038ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e2928884ba2f1fca172580ec18ea497b632ff7ded9c18b5b42e98e368f9218f 0.600000000000 1906837 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": 1418316, "vin": [ { "gen": { "height": 1418306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e2928884ba2f1fca172580ec18ea497b632ff7ded9c18b5b42e98e368f9218f" } } ], "extra": [ 1, 218, 47, 7, 179, 170, 112, 146, 72, 184, 209, 1, 155, 113, 185, 170, 134, 138, 243, 123, 89, 150, 92, 48, 106, 27, 44, 229, 238, 219, 143, 205, 25, 2, 17, 0, 0, 0, 3, 140, 235, 127, 9, 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