Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 754ae6417125ea8b897208f1a844637dc1b06968abe139c4b0834c86f88594b7

Tx prefix hash: c83c865f7f79f445d3be930526fedda22d941aedcf3ab81cfd2bf728574db57a
Tx public key: c8d66d49c0f3731e849253d7929012b6ef2bf1485d92eaff577dc1d08b335d0f
Timestamp: 1676347156 Timestamp [UCT]: 2023-02-14 03:59:16 Age [y:d:h:m:s]: 01:317:07:44:21
Block: 696542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487726 RingCT/type: yes/0
Extra: 01c8d66d49c0f3731e849253d7929012b6ef2bf1485d92eaff577dc1d08b335d0f021100000002835e4d22000000000000000000

1 output(s) for total of 3.020418516000 dcy

stealth address amount amount idx
00: 1da18e9deb51a420a049bc3154fbe31ac03df3f18cb8315f776d368f41b9e14e 3.020418516000 1139571 of 0

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": 696552, "vin": [ { "gen": { "height": 696542 } } ], "vout": [ { "amount": 3020418516, "target": { "key": "1da18e9deb51a420a049bc3154fbe31ac03df3f18cb8315f776d368f41b9e14e" } } ], "extra": [ 1, 200, 214, 109, 73, 192, 243, 115, 30, 132, 146, 83, 215, 146, 144, 18, 182, 239, 43, 241, 72, 93, 146, 234, 255, 87, 125, 193, 208, 139, 51, 93, 15, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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