Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f65e680a756d39c936e75383b2213f11dbd8eedf61f0c3e7b324de9c1e7981f0

Tx prefix hash: ae870b96c812dc2d131107f6fbdcef1f5582823fb0e36ea1a0e9a94490ea830f
Tx public key: e4aa36937374189c4839fbe1af146e7f6e6fe9b7c2812edffad25bc7a56843d3
Timestamp: 1702569275 Timestamp [UCT]: 2023-12-14 15:54:35 Age [y:d:h:m:s]: 01:191:05:03:54
Block: 913043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397632 RingCT/type: yes/0
Extra: 01e4aa36937374189c4839fbe1af146e7f6e6fe9b7c2812edffad25bc7a56843d302110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b104a000aad601522bf28c8a756a0a574c3af34310c17e6ac919a21b219d418a 0.600000000000 1370285 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": 913053, "vin": [ { "gen": { "height": 913043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b104a000aad601522bf28c8a756a0a574c3af34310c17e6ac919a21b219d418a" } } ], "extra": [ 1, 228, 170, 54, 147, 115, 116, 24, 156, 72, 57, 251, 225, 175, 20, 110, 127, 110, 111, 233, 183, 194, 129, 46, 223, 250, 210, 91, 199, 165, 104, 67, 211, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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