Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da0743d97279e6f4dbe99786c8012e556366b7f2af9dd41fcfc7e9d73172b983

Tx prefix hash: dd267be1f7eb83da0ccd0303a3979439f2c724513ed3083ed94f4e05a5e7afd6
Tx public key: cc49cf09a4f88b869cbac23639c267d99805cefd8482f5b255040aaf606a6c27
Timestamp: 1585417001 Timestamp [UCT]: 2020-03-28 17:36:41 Age [y:d:h:m:s]: 04:276:01:13:56
Block: 88946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096247 RingCT/type: yes/0
Extra: 01cc49cf09a4f88b869cbac23639c267d99805cefd8482f5b255040aaf606a6c2702110000000986362411000000000000000000

1 output(s) for total of 311.409524731000 dcy

stealth address amount amount idx
00: 3d6537be0094637e4f2f8f4fa302d115bb468e2bb7faeca58ed7d06f5890a5a4 311.409524731000 159766 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": 88956, "vin": [ { "gen": { "height": 88946 } } ], "vout": [ { "amount": 311409524731, "target": { "key": "3d6537be0094637e4f2f8f4fa302d115bb468e2bb7faeca58ed7d06f5890a5a4" } } ], "extra": [ 1, 204, 73, 207, 9, 164, 248, 139, 134, 156, 186, 194, 54, 57, 194, 103, 217, 152, 5, 206, 253, 132, 130, 245, 178, 85, 4, 10, 175, 96, 106, 108, 39, 2, 17, 0, 0, 0, 9, 134, 54, 36, 17, 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