Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e895b52c590f342424f8c9ae9fb210d9137b60889bd620f3e5ce3ca3262ae71

Tx prefix hash: 3fd013e51a4566878865809da4864bee2834510f94a35e17c6257c734a3400be
Tx public key: 4aef1f4f65c6c505ed06f2aab76c55f96fc7d682a7a1c2c6557a17545e4fab9e
Timestamp: 1576928274 Timestamp [UCT]: 2019-12-21 11:37:54 Age [y:d:h:m:s]: 05:074:08:52:35
Block: 29288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202186 RingCT/type: yes/0
Extra: 014aef1f4f65c6c505ed06f2aab76c55f96fc7d682a7a1c2c6557a17545e4fab9e0211000000289159db1e000000000000000000

1 output(s) for total of 490.859907609000 dcy

stealth address amount amount idx
00: b6a8eae6c4999bb2c6b3d864bc68d0ffbfe124b6b549ab6e9a7944c10e7f4068 490.859907609000 48120 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": 29298, "vin": [ { "gen": { "height": 29288 } } ], "vout": [ { "amount": 490859907609, "target": { "key": "b6a8eae6c4999bb2c6b3d864bc68d0ffbfe124b6b549ab6e9a7944c10e7f4068" } } ], "extra": [ 1, 74, 239, 31, 79, 101, 198, 197, 5, 237, 6, 242, 170, 183, 108, 85, 249, 111, 199, 214, 130, 167, 161, 194, 198, 85, 122, 23, 84, 94, 79, 171, 158, 2, 17, 0, 0, 0, 40, 145, 89, 219, 30, 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