Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e231e328ce000c74174a8cb3da9db0b736d2e4521eea55714ef5c3e695876f1

Tx prefix hash: 3adf2a4e28282e6b0603e0ef241b2a3d5959e3f854ad02211ed49c689b39f33c
Tx public key: cc3ff09a02fd00f0c79c4439588acc9a4b2e4101cd69a6984dcca0b338819557
Timestamp: 1672708583 Timestamp [UCT]: 2023-01-03 01:16:23 Age [y:d:h:m:s]: 02:017:19:33:12
Block: 666349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534603 RingCT/type: yes/0
Extra: 01cc3ff09a02fd00f0c79c4439588acc9a4b2e4101cd69a6984dcca0b33881955702110000000652542ceb000000000000000000

1 output(s) for total of 3.802849261000 dcy

stealth address amount amount idx
00: 8d1fd0b5876feb6d1ee0a8d8cbe3dc731fce7699eb3e3a3a1fd26e6484eceb8c 3.802849261000 1107456 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": 666359, "vin": [ { "gen": { "height": 666349 } } ], "vout": [ { "amount": 3802849261, "target": { "key": "8d1fd0b5876feb6d1ee0a8d8cbe3dc731fce7699eb3e3a3a1fd26e6484eceb8c" } } ], "extra": [ 1, 204, 63, 240, 154, 2, 253, 0, 240, 199, 156, 68, 57, 88, 138, 204, 154, 75, 46, 65, 1, 205, 105, 166, 152, 77, 204, 160, 179, 56, 129, 149, 87, 2, 17, 0, 0, 0, 6, 82, 84, 44, 235, 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