Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9db23a5eaa039f0b2793a546a94ac636fb643c22f992ee28d3ede0f58274e46

Tx prefix hash: 81cff52d9900eacb939f30e01f38d6635404a73f7c1546c5c3a66e109555329a
Tx public key: 65089f3d20802ebf3d10a171470bed6637e165123c82942eff9d0eb525f1bcfd
Timestamp: 1708724630 Timestamp [UCT]: 2024-02-23 21:43:50 Age [y:d:h:m:s]: 01:114:17:00:35
Block: 964076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342935 RingCT/type: yes/0
Extra: 0165089f3d20802ebf3d10a171470bed6637e165123c82942eff9d0eb525f1bcfd02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db58913f0195f2ce5d2169ad31c0d13fe2f319c6392f818ca7aa4b8cc7d9382b 0.600000000000 1423803 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": 964086, "vin": [ { "gen": { "height": 964076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db58913f0195f2ce5d2169ad31c0d13fe2f319c6392f818ca7aa4b8cc7d9382b" } } ], "extra": [ 1, 101, 8, 159, 61, 32, 128, 46, 191, 61, 16, 161, 113, 71, 11, 237, 102, 55, 225, 101, 18, 60, 130, 148, 46, 255, 157, 14, 181, 37, 241, 188, 253, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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