Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 300f3dacdc13285a097ee72d93bb2b68b1541c8dfc925f30029e3dc5f687310c

Tx prefix hash: 4335c3fd4bc79c6c2cb33ecf2ecda9b590daba6a911e883adb234776d10606ea
Tx public key: a3e0bf21f5de518541bf4077959dc946edc4fe2d08a59090e432ec99a1d1a276
Timestamp: 1698330963 Timestamp [UCT]: 2023-10-26 14:36:03 Age [y:d:h:m:s]: 01:217:19:20:59
Block: 878130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416706 RingCT/type: yes/0
Extra: 01a3e0bf21f5de518541bf4077959dc946edc4fe2d08a59090e432ec99a1d1a276021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.755771997000 dcy

stealth address amount amount idx
00: 204418aef2d16f91252e0e2d3e1f84de72a682885de1b6d19f2bfc0af4afb59f 0.755771997000 1333544 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": 878140, "vin": [ { "gen": { "height": 878130 } } ], "vout": [ { "amount": 755771997, "target": { "key": "204418aef2d16f91252e0e2d3e1f84de72a682885de1b6d19f2bfc0af4afb59f" } } ], "extra": [ 1, 163, 224, 191, 33, 245, 222, 81, 133, 65, 191, 64, 119, 149, 157, 201, 70, 237, 196, 254, 45, 8, 165, 144, 144, 228, 50, 236, 153, 161, 209, 162, 118, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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