Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72dfb13e88f81d5ecdfb674bc3d943ddd4a4954f96d932ec8d7ddda357d24739

Tx prefix hash: 656491737c55f48d2d4b941f78a79e2f9554e9973c9e63c85e6da1a955ce2afb
Tx public key: dec2e1e9c04c316a4c6f8d67f19a79c36195f4bfee392ad88a9c47c85729f8ce
Timestamp: 1724591004 Timestamp [UCT]: 2024-08-25 13:03:24 Age [y:d:h:m:s]: 00:276:08:33:13
Block: 1095614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197423 RingCT/type: yes/0
Extra: 01dec2e1e9c04c316a4c6f8d67f19a79c36195f4bfee392ad88a9c47c85729f8ce021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fd597102a31c08c23ca4bd35d60b6da654efcf9b1c943d0fe18a1aef124c2ba 0.600000000000 1570795 of 15

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": 1095624, "vin": [ { "gen": { "height": 1095614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fd597102a31c08c23ca4bd35d60b6da654efcf9b1c943d0fe18a1aef124c2ba" } } ], "extra": [ 1, 222, 194, 225, 233, 192, 76, 49, 106, 76, 111, 141, 103, 241, 154, 121, 195, 97, 149, 244, 191, 238, 57, 42, 216, 138, 156, 71, 200, 87, 41, 248, 206, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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