Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf19a8ca1cbabd19ee3eb758bd3853ebcd6f10e3417ed74c0b9d6aa886143b9

Tx prefix hash: ae053ad95a07f952b3f3718f4ea8bc324a99bbeadcfb34a6d1bcd3884fe25949
Tx public key: d28ab30e2133edff873224466b161881af621d6b536a1a43d4a74d18acaf7f85
Timestamp: 1710388994 Timestamp [UCT]: 2024-03-14 04:03:14 Age [y:d:h:m:s]: 01:264:03:02:25
Block: 977898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447493 RingCT/type: yes/0
Extra: 01d28ab30e2133edff873224466b161881af621d6b536a1a43d4a74d18acaf7f850211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 545d37d8558b2d6ae72b6a4f69bbf0d959f6124d95646db2d5befaf9d5967142 0.600000000000 1437905 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": 977908, "vin": [ { "gen": { "height": 977898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "545d37d8558b2d6ae72b6a4f69bbf0d959f6124d95646db2d5befaf9d5967142" } } ], "extra": [ 1, 210, 138, 179, 14, 33, 51, 237, 255, 135, 50, 36, 70, 107, 22, 24, 129, 175, 98, 29, 107, 83, 106, 26, 67, 212, 167, 77, 24, 172, 175, 127, 133, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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