Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed83722f43d50681dcbb808a41e811d8b0f96b61e1ce47943a4487b0dfb3535

Tx prefix hash: 4142bd9a2ae5210bd0907a7e5f258d328edfaeab6df376385a5ac243408777ab
Tx public key: c1eb5318565f2ed51cd1d2a350d4586bd7b179b1f252a0244e745af1aa988596
Timestamp: 1713646025 Timestamp [UCT]: 2024-04-20 20:47:05 Age [y:d:h:m:s]: 00:353:17:40:30
Block: 1004872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252883 RingCT/type: yes/0
Extra: 01c1eb5318565f2ed51cd1d2a350d4586bd7b179b1f252a0244e745af1aa9885960211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 042c1ab2860ded0b5a1798e02a427fe92ea0af4c011177bfe08cf8825759db8c 0.600000000000 1465446 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": 1004882, "vin": [ { "gen": { "height": 1004872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "042c1ab2860ded0b5a1798e02a427fe92ea0af4c011177bfe08cf8825759db8c" } } ], "extra": [ 1, 193, 235, 83, 24, 86, 95, 46, 213, 28, 209, 210, 163, 80, 212, 88, 107, 215, 177, 121, 177, 242, 82, 160, 36, 78, 116, 90, 241, 170, 152, 133, 150, 2, 17, 0, 0, 0, 6, 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