Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf1f929f0862f338457e1e2a3af11c34e265652b013f71b436b1b7a51726bac

Tx prefix hash: a6d08bdfd9a97fdbb342ba857fc5bbb69efabdd4edaf78a344b7b603b269905a
Tx public key: 8e17e9174ccc21935604e0ecc28445ae4de203741dd15a4ea43ed938fef38470
Timestamp: 1672803257 Timestamp [UCT]: 2023-01-04 03:34:17 Age [y:d:h:m:s]: 02:153:15:18:59
Block: 667148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631520 RingCT/type: yes/0
Extra: 018e17e9174ccc21935604e0ecc28445ae4de203741dd15a4ea43ed938fef3847002110000000d33af99f4000000000000000000

1 output(s) for total of 3.779737950000 dcy

stealth address amount amount idx
00: a20ed451faea6b5b75357210eeb7a5a57ec18c1946e4dc656618693cedcecbf4 3.779737950000 1108313 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": 667158, "vin": [ { "gen": { "height": 667148 } } ], "vout": [ { "amount": 3779737950, "target": { "key": "a20ed451faea6b5b75357210eeb7a5a57ec18c1946e4dc656618693cedcecbf4" } } ], "extra": [ 1, 142, 23, 233, 23, 76, 204, 33, 147, 86, 4, 224, 236, 194, 132, 69, 174, 77, 226, 3, 116, 29, 209, 90, 78, 164, 62, 217, 56, 254, 243, 132, 112, 2, 17, 0, 0, 0, 13, 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