Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d8d114b08c3f026d8e254b6d1c423cbb0087469839a1043901d39f5e3e65f67

Tx prefix hash: bb8ca6ca73b9184d0d40a3af6db539d0770bca0429d320177177ffa5136c891a
Tx public key: 3d2c28654f14e4f1cbb5cf3142798e401dedccf313dbed19cf06bca3f2484787
Timestamp: 1632148270 Timestamp [UCT]: 2021-09-20 14:31:10 Age [y:d:h:m:s]: 03:236:03:44:02
Block: 337579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 944621 RingCT/type: yes/0
Extra: 013d2c28654f14e4f1cbb5cf3142798e401dedccf313dbed19cf06bca3f248478702110000001b5410958b000000000000000000

1 output(s) for total of 46.715507689000 dcy

stealth address amount amount idx
00: 514a9a086ed4a7d173897c6604a082dc9d076ca0bc494b2199c47cf182010d02 46.715507689000 695068 of 0

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": 337589, "vin": [ { "gen": { "height": 337579 } } ], "vout": [ { "amount": 46715507689, "target": { "key": "514a9a086ed4a7d173897c6604a082dc9d076ca0bc494b2199c47cf182010d02" } } ], "extra": [ 1, 61, 44, 40, 101, 79, 20, 228, 241, 203, 181, 207, 49, 66, 121, 142, 64, 29, 237, 204, 243, 19, 219, 237, 25, 207, 6, 188, 163, 242, 72, 71, 135, 2, 17, 0, 0, 0, 27, 84, 16, 149, 139, 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