Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9f5134079501de96579c65b8002e5f2afd44c2aaf8eec5a9209c79fcfd4907

Tx prefix hash: 3a933c5980d8ffdb93ffe55da36741a5ac182ac0cbccdbe87fb0eb9dd316eb54
Tx public key: 9d79a13472e8a43b857b5003aa9c99a6c59080e62c84e5a4d92edf6d499dcef9
Timestamp: 1713123562 Timestamp [UCT]: 2024-04-14 19:39:22 Age [y:d:h:m:s]: 01:204:16:25:47
Block: 1000523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404955 RingCT/type: yes/0
Extra: 019d79a13472e8a43b857b5003aa9c99a6c59080e62c84e5a4d92edf6d499dcef902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fcb639325e571eb6bccee2ad0ca7b9a6bb3fb664aa23d63043790f56d1e72ba 0.600000000000 1461021 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": 1000533, "vin": [ { "gen": { "height": 1000523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fcb639325e571eb6bccee2ad0ca7b9a6bb3fb664aa23d63043790f56d1e72ba" } } ], "extra": [ 1, 157, 121, 161, 52, 114, 232, 164, 59, 133, 123, 80, 3, 170, 156, 153, 166, 197, 144, 128, 230, 44, 132, 229, 164, 217, 46, 223, 109, 73, 157, 206, 249, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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