Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44c23c8dc89ecc5f598354f47a34cca86a4f737263cd56ff00084deb776c9ac

Tx prefix hash: fd0fb3ffcd8a39131898576688bc0c0f4fa31555081d7cd7ceb14f345febfcb4
Tx public key: 987ae65ced03ae71337bf6956ae9df75e67fc7f6bb83b829ae9330e3d253488c
Timestamp: 1722917141 Timestamp [UCT]: 2024-08-06 04:05:41 Age [y:d:h:m:s]: 00:301:03:35:59
Block: 1081737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215175 RingCT/type: yes/0
Extra: 01987ae65ced03ae71337bf6956ae9df75e67fc7f6bb83b829ae9330e3d253488c021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0061ea8263bfbdd3cb6d13f1cb3ea331d597eac180ae97b9df9938a650fe80cc 0.600000000000 1555558 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": 1081747, "vin": [ { "gen": { "height": 1081737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0061ea8263bfbdd3cb6d13f1cb3ea331d597eac180ae97b9df9938a650fe80cc" } } ], "extra": [ 1, 152, 122, 230, 92, 237, 3, 174, 113, 51, 123, 246, 149, 106, 233, 223, 117, 230, 127, 199, 246, 187, 131, 184, 41, 174, 147, 48, 227, 210, 83, 72, 140, 2, 17, 0, 0, 0, 9, 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