Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4c3152ed922d6cb69f9d936cca3fadf250a08d398c8a0674ea1eda045aab20f

Tx prefix hash: 73e8172ae2454bfe4ccfab3d0b650ee1cb1f32315d30633fb452f829c78ea907
Tx public key: 88cbe4a0550f1bd33b1f944f87daeb45a06f13b7b9b628726ea1486751cfc9e1
Timestamp: 1688317773 Timestamp [UCT]: 2023-07-02 17:09:33 Age [y:d:h:m:s]: 01:241:02:02:14
Block: 795156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433408 RingCT/type: yes/0
Extra: 0188cbe4a0550f1bd33b1f944f87daeb45a06f13b7b9b628726ea1486751cfc9e102110000000575e3f0e9000000000000000000

1 output(s) for total of 1.423371363000 dcy

stealth address amount amount idx
00: 3a4e1acdd659cd595a5d7d14bd504c66a096d730ae2f592c20139f725c6f6def 1.423371363000 1245945 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": 795166, "vin": [ { "gen": { "height": 795156 } } ], "vout": [ { "amount": 1423371363, "target": { "key": "3a4e1acdd659cd595a5d7d14bd504c66a096d730ae2f592c20139f725c6f6def" } } ], "extra": [ 1, 136, 203, 228, 160, 85, 15, 27, 211, 59, 31, 148, 79, 135, 218, 235, 69, 160, 111, 19, 183, 185, 182, 40, 114, 110, 161, 72, 103, 81, 207, 201, 225, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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