Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46088bba28313af1307a09125e652198a343a7c2927ac4bcf396577736f23c61

Tx prefix hash: bf66d359cfe9a61aaebb65c4b0b4af7d84d7b371055702e65300139d2a02d4fa
Tx public key: 476bcd35f18b9d44af3a4de50c2e0943d0b33de56c1b08e3f89399db7bbb5ccc
Timestamp: 1709463179 Timestamp [UCT]: 2024-03-03 10:52:59 Age [y:d:h:m:s]: 01:267:16:23:59
Block: 970204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450053 RingCT/type: yes/0
Extra: 01476bcd35f18b9d44af3a4de50c2e0943d0b33de56c1b08e3f89399db7bbb5ccc02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68450e8bc3feb71af787e89b49b009359be36b015d5a45b9202abe0c7d757fb7 0.600000000000 1430053 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": 970214, "vin": [ { "gen": { "height": 970204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68450e8bc3feb71af787e89b49b009359be36b015d5a45b9202abe0c7d757fb7" } } ], "extra": [ 1, 71, 107, 205, 53, 241, 139, 157, 68, 175, 58, 77, 229, 12, 46, 9, 67, 208, 179, 61, 229, 108, 27, 8, 227, 248, 147, 153, 219, 123, 187, 92, 204, 2, 17, 0, 0, 0, 4, 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