Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf61d90d2fe518bf2bd38950825b34a9f770ab4b01a2198bc557ada7994bcc7

Tx prefix hash: 68ee2489e4feaa21ad4757ee5f29af23602b1d699c3518110eea9e60db5edf08
Tx public key: f519f6ec8960f2c346a723fdf1aee686a3f6b8b8c2a1efba40597fafc78bd899
Timestamp: 1724321155 Timestamp [UCT]: 2024-08-22 10:05:55 Age [y:d:h:m:s]: 00:237:19:49:01
Block: 1093391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169841 RingCT/type: yes/0
Extra: 01f519f6ec8960f2c346a723fdf1aee686a3f6b8b8c2a1efba40597fafc78bd899021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67aaa667875e2b2f5944d39dc9295ffe5445af22c283079dd6a83b9506866a5f 0.600000000000 1568326 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": 1093401, "vin": [ { "gen": { "height": 1093391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67aaa667875e2b2f5944d39dc9295ffe5445af22c283079dd6a83b9506866a5f" } } ], "extra": [ 1, 245, 25, 246, 236, 137, 96, 242, 195, 70, 167, 35, 253, 241, 174, 230, 134, 163, 246, 184, 184, 194, 161, 239, 186, 64, 89, 127, 175, 199, 139, 216, 153, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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