Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c45fa71c258338936004b392c2a1f7c5e991a0e483044de947847dfb46d376f

Tx prefix hash: cfbeb9115851d10928db7e4acd3940084dc70a93ada46cd4dfd44059d5513296
Tx public key: 425dc2820e15786ea4e6aea38dcb246f1cfcb732e0f9f3bdd8b206198dd09f2a
Timestamp: 1728850094 Timestamp [UCT]: 2024-10-13 20:08:14 Age [y:d:h:m:s]: 00:249:10:01:28
Block: 1130930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177945 RingCT/type: yes/0
Extra: 01425dc2820e15786ea4e6aea38dcb246f1cfcb732e0f9f3bdd8b206198dd09f2a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6285ea2e76abe4ed8f0ecbffd0de405e2d55a242d4d9286bfccb9b9f8b80f4 0.600000000000 1613811 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": 1130940, "vin": [ { "gen": { "height": 1130930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6285ea2e76abe4ed8f0ecbffd0de405e2d55a242d4d9286bfccb9b9f8b80f4" } } ], "extra": [ 1, 66, 93, 194, 130, 14, 21, 120, 110, 164, 230, 174, 163, 141, 203, 36, 111, 28, 252, 183, 50, 224, 249, 243, 189, 216, 178, 6, 25, 141, 208, 159, 42, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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