Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db11cf6a3750f240e6d543dbe3df026a0f2db5690b7663d4a391fca8d62becd1

Tx prefix hash: 8f8f87423e96ca6d1b28cb31338ab11e43714d86664f3d6ad2d201d15d74015c
Tx public key: 8f651abae81130b8d105fcfaf6deef6cfbe1f93c7af29f6bfd77b83af1f5d83e
Timestamp: 1725317436 Timestamp [UCT]: 2024-09-02 22:50:36 Age [y:d:h:m:s]: 01:066:04:06:11
Block: 1101644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305720 RingCT/type: yes/0
Extra: 018f651abae81130b8d105fcfaf6deef6cfbe1f93c7af29f6bfd77b83af1f5d83e02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e432275655fb4b3dd6bf3b849981ab6caa468628983d46c045dea3749b90f5f 0.600000000000 1577771 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": 1101654, "vin": [ { "gen": { "height": 1101644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e432275655fb4b3dd6bf3b849981ab6caa468628983d46c045dea3749b90f5f" } } ], "extra": [ 1, 143, 101, 26, 186, 232, 17, 48, 184, 209, 5, 252, 250, 246, 222, 239, 108, 251, 225, 249, 60, 122, 242, 159, 107, 253, 119, 184, 58, 241, 245, 216, 62, 2, 17, 0, 0, 0, 10, 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