Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40a08131cccd1e9fb3cf9cb9b6e534d323800eac53d1207f8fc960127684a866

Tx prefix hash: 448c3277c451c1bbdadc77a49e2936792374b9a4b530a527c3de319e2515d768
Tx public key: f3153127c61140b989bfe3f50492417c0c4913c3fce8d5fb637bf076e7be876a
Timestamp: 1707344003 Timestamp [UCT]: 2024-02-07 22:13:23 Age [y:d:h:m:s]: 00:267:02:30:15
Block: 952631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191254 RingCT/type: yes/0
Extra: 01f3153127c61140b989bfe3f50492417c0c4913c3fce8d5fb637bf076e7be876a02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 159dbed4b597b928b3d175dbfa52c0c282381bb2b29583590d11c6f3e91b78ff 0.600000000000 1411715 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": 952641, "vin": [ { "gen": { "height": 952631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "159dbed4b597b928b3d175dbfa52c0c282381bb2b29583590d11c6f3e91b78ff" } } ], "extra": [ 1, 243, 21, 49, 39, 198, 17, 64, 185, 137, 191, 227, 245, 4, 146, 65, 124, 12, 73, 19, 195, 252, 232, 213, 251, 99, 123, 240, 118, 231, 190, 135, 106, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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