Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22453de619c8bcfde468cc54f2b73cb948bca1094e8cbc8164ec49de63b043fb

Tx prefix hash: 05c9dbef201abb183f743324cecfe3422d6be270e28773239e5eaace0c5a7910
Tx public key: 0d3e21d721f529cfef94d0176b67a11f41eb272eed52229d1a19bdb03642e7bc
Timestamp: 1696281692 Timestamp [UCT]: 2023-10-02 21:21:32 Age [y:d:h:m:s]: 01:195:07:28:01
Block: 861121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400642 RingCT/type: yes/0
Extra: 010d3e21d721f529cfef94d0176b67a11f41eb272eed52229d1a19bdb03642e7bc0211000000064b8f5122000000000000000000

1 output(s) for total of 0.860535689000 dcy

stealth address amount amount idx
00: 1a222a95e5d0cc00cc7b32adf90e2a6f808ccfec53eb8aa4c17814304dd399a2 0.860535689000 1315437 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": 861131, "vin": [ { "gen": { "height": 861121 } } ], "vout": [ { "amount": 860535689, "target": { "key": "1a222a95e5d0cc00cc7b32adf90e2a6f808ccfec53eb8aa4c17814304dd399a2" } } ], "extra": [ 1, 13, 62, 33, 215, 33, 245, 41, 207, 239, 148, 208, 23, 107, 103, 161, 31, 65, 235, 39, 46, 237, 82, 34, 157, 26, 25, 189, 176, 54, 66, 231, 188, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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