Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ceafa4b61b55956902a8cbfd846e27332ee90e181fad2cfbd7d77209895206f

Tx prefix hash: 0e231a5effa058e5737bc1f8d07084a1e4c47dc2074a2537b80e3659fbeee21d
Tx public key: 65c2cf50611c40a56a416dd76d17801250cb015b808d80132c56e7a60939b2c4
Timestamp: 1697320513 Timestamp [UCT]: 2023-10-14 21:55:13 Age [y:d:h:m:s]: 01:109:14:42:56
Block: 869737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339335 RingCT/type: yes/0
Extra: 0165c2cf50611c40a56a416dd76d17801250cb015b808d80132c56e7a60939b2c40211000000054b8f5122000000000000000000

1 output(s) for total of 0.805749977000 dcy

stealth address amount amount idx
00: 601417d345d15017cd0751cae125ea0e671fc9c2a01ae3f5727524c745e3b79c 0.805749977000 1324592 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": 869747, "vin": [ { "gen": { "height": 869737 } } ], "vout": [ { "amount": 805749977, "target": { "key": "601417d345d15017cd0751cae125ea0e671fc9c2a01ae3f5727524c745e3b79c" } } ], "extra": [ 1, 101, 194, 207, 80, 97, 28, 64, 165, 106, 65, 109, 215, 109, 23, 128, 18, 80, 203, 1, 91, 128, 141, 128, 19, 44, 86, 231, 166, 9, 57, 178, 196, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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