Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c1a9409e0878db32a6d5748a78fa1d73ccd96a06adae823827248da078e38f0

Tx prefix hash: 4d1185e9e982d390c9e039499dbbb5321bca7f8dbec6e7d8aec4e1ee7ff70203
Tx public key: ad41beaa721a49d744bdadb9b2bcd75164e0fe50c65a4ce9c0c9cc4dd372fab2
Timestamp: 1729694673 Timestamp [UCT]: 2024-10-23 14:44:33 Age [y:d:h:m:s]: 00:141:21:35:15
Block: 1137896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101231 RingCT/type: yes/0
Extra: 01ad41beaa721a49d744bdadb9b2bcd75164e0fe50c65a4ce9c0c9cc4dd372fab20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25eb8499fb43273c4948ce014dd4d166a8d37fa4d38082e34035b58a12040068 0.600000000000 1621479 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": 1137906, "vin": [ { "gen": { "height": 1137896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25eb8499fb43273c4948ce014dd4d166a8d37fa4d38082e34035b58a12040068" } } ], "extra": [ 1, 173, 65, 190, 170, 114, 26, 73, 215, 68, 189, 173, 185, 178, 188, 215, 81, 100, 224, 254, 80, 198, 90, 76, 233, 192, 201, 204, 77, 211, 114, 250, 178, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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