Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cad3d9109dcdb208ebbf2ef7665eee589c9e56a63a1e4d123470a96472278e6

Tx prefix hash: 676c3be5253793c97602efaacfcc409c3cc18ea4fca161714a8efc2dccae996c
Tx public key: 79da4f2e6e3cfa23176cb045ee1c8c1305971995fa0a7cff76799b599caec6d3
Timestamp: 1619445048 Timestamp [UCT]: 2021-04-26 13:50:48 Age [y:d:h:m:s]: 04:189:04:03:01
Block: 248260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153832 RingCT/type: yes/0
Extra: 0179da4f2e6e3cfa23176cb045ee1c8c1305971995fa0a7cff76799b599caec6d30211000000a9cc643473000000000000000000

1 output(s) for total of 92.347931156000 dcy

stealth address amount amount idx
00: 8f4901d54bd82ab4e665e8867a61baf6c775e4e8a39eb51a5fb6d52da702ff73 92.347931156000 519816 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": 248270, "vin": [ { "gen": { "height": 248260 } } ], "vout": [ { "amount": 92347931156, "target": { "key": "8f4901d54bd82ab4e665e8867a61baf6c775e4e8a39eb51a5fb6d52da702ff73" } } ], "extra": [ 1, 121, 218, 79, 46, 110, 60, 250, 35, 23, 108, 176, 69, 238, 28, 140, 19, 5, 151, 25, 149, 250, 10, 124, 255, 118, 121, 155, 89, 156, 174, 198, 211, 2, 17, 0, 0, 0, 169, 204, 100, 52, 115, 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