Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37cd7956746cf8add32a98f2bc276cb6ba44d4ae11e1254949d246428232f87d

Tx prefix hash: ac3359c1721797fd4abb9cf369020bcefec0f8b54651c469bdb2084c11c762bf
Tx public key: e016a4435d00f2e6a1c0de85d0a8a888e54fdf964cf575052fe637fa9f9232f8
Timestamp: 1704021301 Timestamp [UCT]: 2023-12-31 11:15:01 Age [y:d:h:m:s]: 01:165:22:57:40
Block: 925074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379703 RingCT/type: yes/0
Extra: 01e016a4435d00f2e6a1c0de85d0a8a888e54fdf964cf575052fe637fa9f9232f80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3f10369b199ed881a0d402e47131fe1a242ad080c94d3ae282e180750d32b63 0.600000000000 1382834 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": 925084, "vin": [ { "gen": { "height": 925074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3f10369b199ed881a0d402e47131fe1a242ad080c94d3ae282e180750d32b63" } } ], "extra": [ 1, 224, 22, 164, 67, 93, 0, 242, 230, 161, 192, 222, 133, 208, 168, 168, 136, 229, 79, 223, 150, 76, 245, 117, 5, 47, 230, 55, 250, 159, 146, 50, 248, 2, 17, 0, 0, 0, 1, 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