Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 723e2f96ce7e41cbb951c6fc7dd49e98dbe0c2b00c767874419aab5972a2f1d9

Tx prefix hash: 7bb101a7013951f296a8464fbb52fe547c3ac7a0b3b3c2a0ba4e0a7630a402bd
Tx public key: 5e2f6fe5fe9ec1b7b40b8bb8c0c5a0df420e4444feb5886a5bc9b10f91bf9664
Timestamp: 1745280512 Timestamp [UCT]: 2025-04-22 00:08:32 Age [y:d:h:m:s]: 00:256:07:43:21
Block: 1266623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180991 RingCT/type: yes/0
Extra: 015e2f6fe5fe9ec1b7b40b8bb8c0c5a0df420e4444feb5886a5bc9b10f91bf9664021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfd37583a72216ac53d3e72b06a1e932ac4735edac5a83c8c52f82cd0064dca0 0.600000000000 1753844 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": 1266633, "vin": [ { "gen": { "height": 1266623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfd37583a72216ac53d3e72b06a1e932ac4735edac5a83c8c52f82cd0064dca0" } } ], "extra": [ 1, 94, 47, 111, 229, 254, 158, 193, 183, 180, 11, 139, 184, 192, 197, 160, 223, 66, 14, 68, 68, 254, 181, 136, 106, 91, 201, 177, 15, 145, 191, 150, 100, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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