Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aed92e116f9581f39e2d2f558f62cfcf5ee2e64346b5f0b1e79530ccd848d0b1

Tx prefix hash: 8862a5af85210854226f58325fab96a4a7f013b50070b641680a733e6580e45a
Tx public key: f835294daaf5c3855805536c8bd54a5454cf14f6640873d5d23b91d154314457
Timestamp: 1576967534 Timestamp [UCT]: 2019-12-21 22:32:14 Age [y:d:h:m:s]: 05:293:04:43:24
Block: 29438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1356457 RingCT/type: yes/0
Extra: 01f835294daaf5c3855805536c8bd54a5454cf14f6640873d5d23b91d15431445702110000002fd81c26c0000000000000000000

1 output(s) for total of 490.298482195000 dcy

stealth address amount amount idx
00: de8868b5e82d19db4d7a09263cfb33ea746ae10d123b1b4af675c837420c2ec6 490.298482195000 48412 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": 29448, "vin": [ { "gen": { "height": 29438 } } ], "vout": [ { "amount": 490298482195, "target": { "key": "de8868b5e82d19db4d7a09263cfb33ea746ae10d123b1b4af675c837420c2ec6" } } ], "extra": [ 1, 248, 53, 41, 77, 170, 245, 195, 133, 88, 5, 83, 108, 139, 213, 74, 84, 84, 207, 20, 246, 100, 8, 115, 213, 210, 59, 145, 209, 84, 49, 68, 87, 2, 17, 0, 0, 0, 47, 216, 28, 38, 192, 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