Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc33303fe2274da4e073ba2ed633a9508175bae05d640962cfb5a2af62c5e21f

Tx prefix hash: 32df0e929ce7503d881a3dbf1c0a8d57415b5fa113759881d210a3f611d46c20
Tx public key: 57d243c942d86ffeb78f3d6f5a2e178f31be84c08e8dee17043e88586182027d
Timestamp: 1731058561 Timestamp [UCT]: 2024-11-08 09:36:01 Age [y:d:h:m:s]: 00:016:00:59:09
Block: 1149153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11472 RingCT/type: yes/0
Extra: 0157d243c942d86ffeb78f3d6f5a2e178f31be84c08e8dee17043e88586182027d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 648effc802a583ad73af6a7b5697f4ce803977730804e7de7918f162c113b11c 0.600000000000 1634168 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": 1149163, "vin": [ { "gen": { "height": 1149153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "648effc802a583ad73af6a7b5697f4ce803977730804e7de7918f162c113b11c" } } ], "extra": [ 1, 87, 210, 67, 201, 66, 216, 111, 254, 183, 143, 61, 111, 90, 46, 23, 143, 49, 190, 132, 192, 142, 141, 238, 23, 4, 62, 136, 88, 97, 130, 2, 125, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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