Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5df8780f47870d72a2f9157a116d5ff36cd74f68c997b839e65157f4877a225

Tx prefix hash: b4bedc70076f86d10f9599f883b7832f31aab8b3abc1da086eea55f998d111b0
Tx public key: a7e44e7ee2e00b408dfe6b4bca9c14f627345dd9cd7e2779b81387086305b878
Timestamp: 1638175629 Timestamp [UCT]: 2021-11-29 08:47:09 Age [y:d:h:m:s]: 03:340:13:42:13
Block: 384554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1019802 RingCT/type: yes/0
Extra: 01a7e44e7ee2e00b408dfe6b4bca9c14f627345dd9cd7e2779b81387086305b878021100000002b494d89c000000000000000000

1 output(s) for total of 32.645889177000 dcy

stealth address amount amount idx
00: be847cb28be6c32ff2d82104f9e57800d0148101efb7d9ea8d444691e2a4969a 32.645889177000 776143 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": 384564, "vin": [ { "gen": { "height": 384554 } } ], "vout": [ { "amount": 32645889177, "target": { "key": "be847cb28be6c32ff2d82104f9e57800d0148101efb7d9ea8d444691e2a4969a" } } ], "extra": [ 1, 167, 228, 78, 126, 226, 224, 11, 64, 141, 254, 107, 75, 202, 156, 20, 246, 39, 52, 93, 217, 205, 126, 39, 121, 184, 19, 135, 8, 99, 5, 184, 120, 2, 17, 0, 0, 0, 2, 180, 148, 216, 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