Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adfed93bbccd01b583ee2e2f3edd8d3ac849ee7548f328bac2538735456ab8f2

Tx prefix hash: 08bfe0dfe5f94716d1d150f89fa7b713c1d1240d7a54b541d7e13f90bc0a0d4d
Tx public key: e2568b45ca2477d414b8fd2ccc3ee15b3d5098845531de6750f97d454ceee487
Timestamp: 1700613750 Timestamp [UCT]: 2023-11-22 00:42:30 Age [y:d:h:m:s]: 01:132:02:25:15
Block: 896837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355562 RingCT/type: yes/0
Extra: 01e2568b45ca2477d414b8fd2ccc3ee15b3d5098845531de6750f97d454ceee48702110000000933af99f4000000000000000000

1 output(s) for total of 0.655249521000 dcy

stealth address amount amount idx
00: 131e011d1000c0751415abf8a0ea5884a224674f06bae47905895556cbbb6e54 0.655249521000 1353180 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": 896847, "vin": [ { "gen": { "height": 896837 } } ], "vout": [ { "amount": 655249521, "target": { "key": "131e011d1000c0751415abf8a0ea5884a224674f06bae47905895556cbbb6e54" } } ], "extra": [ 1, 226, 86, 139, 69, 202, 36, 119, 212, 20, 184, 253, 44, 204, 62, 225, 91, 61, 80, 152, 132, 85, 49, 222, 103, 80, 249, 125, 69, 76, 238, 228, 135, 2, 17, 0, 0, 0, 9, 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