Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2128bf870fe2156922f06276a0f5f57e994518a6292d4c3b27d5f6583faf9539

Tx prefix hash: 85cfc3fe355a362fb208c1702fd0396e6fead894877699815358a0b0c21f8d84
Tx public key: a5242f887162c825be57f0c55b25fb3b468d82b0ea433ae0e15941f59f755b3e
Timestamp: 1577564113 Timestamp [UCT]: 2019-12-28 20:15:13 Age [y:d:h:m:s]: 04:313:14:17:07
Block: 33802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113228 RingCT/type: yes/0
Extra: 01a5242f887162c825be57f0c55b25fb3b468d82b0ea433ae0e15941f59f755b3e021100000058c5b5978f000000000000000000

1 output(s) for total of 474.263597577000 dcy

stealth address amount amount idx
00: 0b81f9aa3b0d05cb3d3f71edfd0f3fed3555936ef1f394610885d15c1e3d8a81 474.263597577000 56723 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": 33812, "vin": [ { "gen": { "height": 33802 } } ], "vout": [ { "amount": 474263597577, "target": { "key": "0b81f9aa3b0d05cb3d3f71edfd0f3fed3555936ef1f394610885d15c1e3d8a81" } } ], "extra": [ 1, 165, 36, 47, 136, 113, 98, 200, 37, 190, 87, 240, 197, 91, 37, 251, 59, 70, 141, 130, 176, 234, 67, 58, 224, 225, 89, 65, 245, 159, 117, 91, 62, 2, 17, 0, 0, 0, 88, 197, 181, 151, 143, 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