Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1497a536cee5199f34f9ef598cc4488b3459fb51bac7cff22b751a575a5097cd

Tx prefix hash: 797d430f8053ac6a430952f01b304e053ee4d7a48d053f748d8734ef07e6f1a5
Tx public key: ca44158ea56b50754e1e3e03afc1f471853d4d41cf580fdbb23d8d10c2eda036
Timestamp: 1722312655 Timestamp [UCT]: 2024-07-30 04:10:55 Age [y:d:h:m:s]: 00:086:03:16:09
Block: 1076729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61668 RingCT/type: yes/0
Extra: 01ca44158ea56b50754e1e3e03afc1f471853d4d41cf580fdbb23d8d10c2eda03602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b8e3304f3eeee9dfe88284e7466d9b2717fffc67221ff527d6835c6011bae88 0.600000000000 1549270 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": 1076739, "vin": [ { "gen": { "height": 1076729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b8e3304f3eeee9dfe88284e7466d9b2717fffc67221ff527d6835c6011bae88" } } ], "extra": [ 1, 202, 68, 21, 142, 165, 107, 80, 117, 78, 30, 62, 3, 175, 193, 244, 113, 133, 61, 77, 65, 207, 88, 15, 219, 178, 61, 141, 16, 194, 237, 160, 54, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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