Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60cdb04eb632a45d7f6f88c6bc5ab5571526da319352037ae5ded63dbccbd43e

Tx prefix hash: 8a3fcbde26e8dad292bd3169b1bc54b1b53f3b5e5cf1ef0f1566ce380e24b627
Tx public key: dc4075a13f3c983120d2164834fa3e29c89ac82d8e91759ccfe527eb46c968ce
Timestamp: 1720814792 Timestamp [UCT]: 2024-07-12 20:06:32 Age [y:d:h:m:s]: 00:340:18:13:57
Block: 1064322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243375 RingCT/type: yes/0
Extra: 01dc4075a13f3c983120d2164834fa3e29c89ac82d8e91759ccfe527eb46c968ce02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa78d7e1cd5afe5ea279534e83e7539d7e21ca4c86feaf68b18adf4fbf8fe541 0.600000000000 1534847 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": 1064332, "vin": [ { "gen": { "height": 1064322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa78d7e1cd5afe5ea279534e83e7539d7e21ca4c86feaf68b18adf4fbf8fe541" } } ], "extra": [ 1, 220, 64, 117, 161, 63, 60, 152, 49, 32, 210, 22, 72, 52, 250, 62, 41, 200, 154, 200, 45, 142, 145, 117, 156, 207, 229, 39, 235, 70, 201, 104, 206, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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