Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83e7e10829ed2b583263a26955e48b4e006313f772b4a7fa6254e60e8be9e16c

Tx prefix hash: cc8493c3f24009b3fe444782dabedf06b1362777adb81826becb29a32754b5d1
Tx public key: 801ffc448e780266599b32df5117167d96b5bddcbc87916c8e25c1f7e758a653
Timestamp: 1702236191 Timestamp [UCT]: 2023-12-10 19:23:11 Age [y:d:h:m:s]: 01:337:06:38:17
Block: 910284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499913 RingCT/type: yes/0
Extra: 01801ffc448e780266599b32df5117167d96b5bddcbc87916c8e25c1f7e758a65302110000000c33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60cab0bfd4e5fb7d4aaab18cf50a53fb7b27cdddae63c4f066a2b05ba17486f3 0.600000000000 1367433 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": 910294, "vin": [ { "gen": { "height": 910284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60cab0bfd4e5fb7d4aaab18cf50a53fb7b27cdddae63c4f066a2b05ba17486f3" } } ], "extra": [ 1, 128, 31, 252, 68, 142, 120, 2, 102, 89, 155, 50, 223, 81, 23, 22, 125, 150, 181, 189, 220, 188, 135, 145, 108, 142, 37, 193, 247, 231, 88, 166, 83, 2, 17, 0, 0, 0, 12, 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