Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3a8d1288e91c8a36f1875eb7b5df557cd8df3ce23d26614af54ed9f92d0ed65

Tx prefix hash: 5994ae33ee058e83cdb5a1b00fde94358b88809f9de912e8efc9e9e117618111
Tx public key: 68e5f55a6c1d1bda0bcc1ea4251dda31e24601105aa1aa8ec6a4da0578d3755f
Timestamp: 1709748364 Timestamp [UCT]: 2024-03-06 18:06:04 Age [y:d:h:m:s]: 01:107:12:14:19
Block: 972573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337690 RingCT/type: yes/0
Extra: 0168e5f55a6c1d1bda0bcc1ea4251dda31e24601105aa1aa8ec6a4da0578d3755f0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fc1b46082bd7dd26f0c740060f4855a0d8b2edd34f38a20e9508fcc4f3e5d1c 0.600000000000 1432488 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": 972583, "vin": [ { "gen": { "height": 972573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fc1b46082bd7dd26f0c740060f4855a0d8b2edd34f38a20e9508fcc4f3e5d1c" } } ], "extra": [ 1, 104, 229, 245, 90, 108, 29, 27, 218, 11, 204, 30, 164, 37, 29, 218, 49, 226, 70, 1, 16, 90, 161, 170, 142, 198, 164, 218, 5, 120, 211, 117, 95, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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