Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055145b663e39d18b8c097d9d59fb0773f5f01f8ff21d6e00c8ecb0280eaf723

Tx prefix hash: 65425c7f387800d3281aa781d632921410a390bf963a02549d6e8701fa94d851
Tx public key: ab09caa1511c92f14f59468e140ded0686f236bc52228c3e38b63c6a6f5f1d5c
Timestamp: 1697299296 Timestamp [UCT]: 2023-10-14 16:01:36 Age [y:d:h:m:s]: 01:194:09:23:41
Block: 869556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399954 RingCT/type: yes/0
Extra: 01ab09caa1511c92f14f59468e140ded0686f236bc52228c3e38b63c6a6f5f1d5c02110000000833af99f4000000000000000000

1 output(s) for total of 0.806863426000 dcy

stealth address amount amount idx
00: b70433c5b196505b59eef80e041156d62cf3b17ed285eeda8fff85afefd57a16 0.806863426000 1324405 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": 869566, "vin": [ { "gen": { "height": 869556 } } ], "vout": [ { "amount": 806863426, "target": { "key": "b70433c5b196505b59eef80e041156d62cf3b17ed285eeda8fff85afefd57a16" } } ], "extra": [ 1, 171, 9, 202, 161, 81, 28, 146, 241, 79, 89, 70, 142, 20, 13, 237, 6, 134, 242, 54, 188, 82, 34, 140, 62, 56, 182, 60, 106, 111, 95, 29, 92, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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