Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ed321cfb029185acb1dd95d733342426dcec186d327944e3262bb89bd05bb5

Tx prefix hash: f4837ef9a94a30cafac07914a1b72c5c43c8d8ef6e4ce6446b6cde8013fd38d3
Tx public key: 74b62ae66b50b80faab1701d409e2d7c72f56976b79a82e872c6f7b5bd570dc3
Timestamp: 1723281379 Timestamp [UCT]: 2024-08-10 09:16:19 Age [y:d:h:m:s]: 00:074:19:10:10
Block: 1084764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53541 RingCT/type: yes/0
Extra: 0174b62ae66b50b80faab1701d409e2d7c72f56976b79a82e872c6f7b5bd570dc3021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db9a8649ff5590d4085545a79f7cf91d460fd752fb56b9cb800af38b7fd3c3b 0.600000000000 1559155 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": 1084774, "vin": [ { "gen": { "height": 1084764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db9a8649ff5590d4085545a79f7cf91d460fd752fb56b9cb800af38b7fd3c3b" } } ], "extra": [ 1, 116, 182, 42, 230, 107, 80, 184, 15, 170, 177, 112, 29, 64, 158, 45, 124, 114, 245, 105, 118, 183, 154, 130, 232, 114, 198, 247, 181, 189, 87, 13, 195, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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