Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31969a92748b2df6d42629679afae4a8c8ad0daf10d23679b4afb407dbb6f534

Tx prefix hash: 371cd485c580dfd4c9605a4632ac89f8a73823e1c76ca7378ad42dfbb09a8947
Tx public key: 3e67fa2ca421b312d8078709fd57459bfa6fe6e23f15c9f45d5f9274bd63a702
Timestamp: 1685597244 Timestamp [UCT]: 2023-06-01 05:27:24 Age [y:d:h:m:s]: 02:163:16:06:58
Block: 772595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636756 RingCT/type: yes/0
Extra: 013e67fa2ca421b312d8078709fd57459bfa6fe6e23f15c9f45d5f9274bd63a702021100000002faf35c9c000000000000000000

1 output(s) for total of 1.690722046000 dcy

stealth address amount amount idx
00: fd86323686b10358464acc6fe335cdf8181bd9a2f393e9beb806c2174e13242e 1.690722046000 1222010 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": 772605, "vin": [ { "gen": { "height": 772595 } } ], "vout": [ { "amount": 1690722046, "target": { "key": "fd86323686b10358464acc6fe335cdf8181bd9a2f393e9beb806c2174e13242e" } } ], "extra": [ 1, 62, 103, 250, 44, 164, 33, 179, 18, 216, 7, 135, 9, 253, 87, 69, 155, 250, 111, 230, 226, 63, 21, 201, 244, 93, 95, 146, 116, 189, 99, 167, 2, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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