Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d7565caaa4762b10f9552b2e5ca2156e5089851e5faf9ef10aac4c6d1d2ff2c

Tx prefix hash: ec679325a43eb19ae66836e476701dc058abc5a20b4a908e13c4b35b4924f03f
Tx public key: 4574ac66f68c355f6db4d5af6ee892dfc030689b2dd57c59dd4016ba52cec581
Timestamp: 1670408414 Timestamp [UCT]: 2022-12-07 10:20:14 Age [y:d:h:m:s]: 02:082:16:41:42
Block: 647297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580783 RingCT/type: yes/0
Extra: 014574ac66f68c355f6db4d5af6ee892dfc030689b2dd57c59dd4016ba52cec5810211000000017e406890000000000000000000

1 output(s) for total of 4.397808595000 dcy

stealth address amount amount idx
00: fee5fd1fc94e0cc59f75bb562cab2ab39e88f1629a7d5d12ab8063dea3d2ec77 4.397808595000 1087564 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": 647307, "vin": [ { "gen": { "height": 647297 } } ], "vout": [ { "amount": 4397808595, "target": { "key": "fee5fd1fc94e0cc59f75bb562cab2ab39e88f1629a7d5d12ab8063dea3d2ec77" } } ], "extra": [ 1, 69, 116, 172, 102, 246, 140, 53, 95, 109, 180, 213, 175, 110, 232, 146, 223, 192, 48, 104, 155, 45, 213, 124, 89, 221, 64, 22, 186, 82, 206, 197, 129, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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