Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 092e5dc3c0032befc1a2ada396e1d24744f26db6a37a127c5cd3d37ca7485929

Tx prefix hash: 896d0c5f5d9c0bafd13ad67b8d31516daa188bfe88d8396dd6bc84d0a7e585f6
Tx public key: f57928e85dffbaab004d5ce4e1359c448ecee9d85c56a21a5ff13a8198920cf2
Timestamp: 1715328470 Timestamp [UCT]: 2024-05-10 08:07:50 Age [y:d:h:m:s]: 00:313:20:58:28
Block: 1018832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224358 RingCT/type: yes/0
Extra: 01f57928e85dffbaab004d5ce4e1359c448ecee9d85c56a21a5ff13a8198920cf202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e09121f63f103f794dcb63f1a6fa6da5aa7c81d8b1d8b86c7fe210fd07a409b4 0.600000000000 1482627 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": 1018842, "vin": [ { "gen": { "height": 1018832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e09121f63f103f794dcb63f1a6fa6da5aa7c81d8b1d8b86c7fe210fd07a409b4" } } ], "extra": [ 1, 245, 121, 40, 232, 93, 255, 186, 171, 0, 77, 92, 228, 225, 53, 156, 68, 142, 206, 233, 216, 92, 86, 162, 26, 95, 241, 58, 129, 152, 146, 12, 242, 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