Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce9b9fe2985efdc297942bbb51290772baa30f34b6126e5d22d53a48c667ebfe

Tx prefix hash: 88060193344257ab1e917cbc96dc3f0034d1e114245e1cac8632c8e223f57ce4
Tx public key: 0146431e7e91265c2e2aa69a59cb543b2fd1750d4b3e956adb31fab528da3fb9
Timestamp: 1648231779 Timestamp [UCT]: 2022-03-25 18:09:39 Age [y:d:h:m:s]: 02:291:04:42:24
Block: 466260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 727649 RingCT/type: yes/0
Extra: 010146431e7e91265c2e2aa69a59cb543b2fd1750d4b3e956adb31fab528da3fb9021100000006a272b9cb000000000000000000

1 output(s) for total of 17.501985561000 dcy

stealth address amount amount idx
00: dfc962e00e1b1a792f4d80ba919e00f8996f1af6e8cb7ff01b84dcc0058ad7a3 17.501985561000 884541 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": 466270, "vin": [ { "gen": { "height": 466260 } } ], "vout": [ { "amount": 17501985561, "target": { "key": "dfc962e00e1b1a792f4d80ba919e00f8996f1af6e8cb7ff01b84dcc0058ad7a3" } } ], "extra": [ 1, 1, 70, 67, 30, 126, 145, 38, 92, 46, 42, 166, 154, 89, 203, 84, 59, 47, 209, 117, 13, 75, 62, 149, 106, 219, 49, 250, 181, 40, 218, 63, 185, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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