Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288377d514dd1c89f065b19f4377078cd1b4c45ecb0ac473e0ff31cfbad84668

Tx prefix hash: a638466405a6350d35ca53f7bd9decbe9df6a9aaa96550e7f0c1db2a0999cfd3
Tx public key: 5680b1d7b21535bb4f4a63d432d8608d9e019f01a3411b12a1a87c45604b94b2
Timestamp: 1665222274 Timestamp [UCT]: 2022-10-08 09:44:34 Age [y:d:h:m:s]: 02:234:19:36:53
Block: 604544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689430 RingCT/type: yes/0
Extra: 015680b1d7b21535bb4f4a63d432d8608d9e019f01a3411b12a1a87c45604b94b2021100000003e6d27f9c000000000000000000

1 output(s) for total of 6.093892981000 dcy

stealth address amount amount idx
00: 79ea4a431a8bc54fd77ad4e5665cb6dee1eb92284b40717248ff673dd1a3be3f 6.093892981000 1040889 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": 604554, "vin": [ { "gen": { "height": 604544 } } ], "vout": [ { "amount": 6093892981, "target": { "key": "79ea4a431a8bc54fd77ad4e5665cb6dee1eb92284b40717248ff673dd1a3be3f" } } ], "extra": [ 1, 86, 128, 177, 215, 178, 21, 53, 187, 79, 74, 99, 212, 50, 216, 96, 141, 158, 1, 159, 1, 163, 65, 27, 18, 161, 168, 124, 69, 96, 75, 148, 178, 2, 17, 0, 0, 0, 3, 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