Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1dd980c24bbc66bcbeeb7d8cbe829a047620cab510079b266f9fef797a97e7c

Tx prefix hash: 30f7f5389bf57565c64e8d68f97a1d0c0d581ade60a950ad2c722fa7516cc73b
Tx public key: 1813c48a5608b38a9455a6c7d61fa6cd2d3f3deb7dd7bb996c2709d0a5481eb6
Timestamp: 1673808761 Timestamp [UCT]: 2023-01-15 18:52:41 Age [y:d:h:m:s]: 02:003:08:45:26
Block: 675462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524297 RingCT/type: yes/0
Extra: 011813c48a5608b38a9455a6c7d61fa6cd2d3f3deb7dd7bb996c2709d0a5481eb60211000000018b7b6602000000000000000000

1 output(s) for total of 3.547430908000 dcy

stealth address amount amount idx
00: 8d81e4160ceee91e9038ba6b55569fc0d872660729519960c016cd483de73d4f 3.547430908000 1117139 of 0

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": 675472, "vin": [ { "gen": { "height": 675462 } } ], "vout": [ { "amount": 3547430908, "target": { "key": "8d81e4160ceee91e9038ba6b55569fc0d872660729519960c016cd483de73d4f" } } ], "extra": [ 1, 24, 19, 196, 138, 86, 8, 179, 138, 148, 85, 166, 199, 214, 31, 166, 205, 45, 63, 61, 235, 125, 215, 187, 153, 108, 39, 9, 208, 165, 72, 30, 182, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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