Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93206f0610d5712aa09a7cdc4df41bca9768c7420e3be18440493b601250126f

Tx prefix hash: 5672c355d63b1dafa59ec56e0091f98671b4601dcd676723d29184164f1bd1e3
Tx public key: da529c0b661b902a7689a375eefa3d2654dc3ca06edf2b0703d6b5fea8e785d7
Timestamp: 1704693817 Timestamp [UCT]: 2024-01-08 06:03:37 Age [y:d:h:m:s]: 00:297:05:12:00
Block: 930633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212851 RingCT/type: yes/0
Extra: 01da529c0b661b902a7689a375eefa3d2654dc3ca06edf2b0703d6b5fea8e785d70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb71f49f6c15552f82d2cab2ead1c1a0934083f4c2e2bca8829a3d1fc0ba103a 0.600000000000 1388519 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": 930643, "vin": [ { "gen": { "height": 930633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb71f49f6c15552f82d2cab2ead1c1a0934083f4c2e2bca8829a3d1fc0ba103a" } } ], "extra": [ 1, 218, 82, 156, 11, 102, 27, 144, 42, 118, 137, 163, 117, 238, 250, 61, 38, 84, 220, 60, 160, 110, 223, 43, 7, 3, 214, 181, 254, 168, 231, 133, 215, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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