Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 260ab97b2f4c95bfe520ae7609830ce95b3db83c0252efcd5eec0a837c262232

Tx prefix hash: 11f97e511c9d1bf1ac10bede243556246d5ef03d0428678a0faa19e7ed9ea84b
Tx public key: 8e39635216f1b9dc6dfa49aa948ef951de68a1fb1458d8f420d3ddbfd73d2eb5
Timestamp: 1703988851 Timestamp [UCT]: 2023-12-31 02:14:11 Age [y:d:h:m:s]: 01:142:07:50:31
Block: 924805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362874 RingCT/type: yes/0
Extra: 018e39635216f1b9dc6dfa49aa948ef951de68a1fb1458d8f420d3ddbfd73d2eb50211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d17150b4a88574929f92ce669dece6d7e35a6b4bbea434328a135ea4bc745d2 0.600000000000 1382563 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": 924815, "vin": [ { "gen": { "height": 924805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d17150b4a88574929f92ce669dece6d7e35a6b4bbea434328a135ea4bc745d2" } } ], "extra": [ 1, 142, 57, 99, 82, 22, 241, 185, 220, 109, 250, 73, 170, 148, 142, 249, 81, 222, 104, 161, 251, 20, 88, 216, 244, 32, 211, 221, 191, 215, 61, 46, 181, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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