Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b07be89a130a3ce67f1b711bab27bae64542eb25d9ca4bb63ab830ba4944fda1

Tx prefix hash: fe431a9c86b8e94c1708e4b6472b35b65ba5145f7b9c15fe782c2647129f691c
Tx public key: 0e098721a76f0f6fab90016443d177606d7c2b864b4dd109bca0a93d2ffb0b6c
Timestamp: 1728807802 Timestamp [UCT]: 2024-10-13 08:23:22 Age [y:d:h:m:s]: 00:242:20:44:24
Block: 1130582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173330 RingCT/type: yes/0
Extra: 010e098721a76f0f6fab90016443d177606d7c2b864b4dd109bca0a93d2ffb0b6c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd501fcf16994a75799b7105caf63c1a839ebdc10c1be121a5f5d11e449c482e 0.600000000000 1613459 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": 1130592, "vin": [ { "gen": { "height": 1130582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd501fcf16994a75799b7105caf63c1a839ebdc10c1be121a5f5d11e449c482e" } } ], "extra": [ 1, 14, 9, 135, 33, 167, 111, 15, 111, 171, 144, 1, 100, 67, 209, 119, 96, 109, 124, 43, 134, 75, 77, 209, 9, 188, 160, 169, 61, 47, 251, 11, 108, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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