Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ece97c554519dcdac936ff78e3fba8241bfd909f308e06d458e7daeac34d089

Tx prefix hash: 2ca2a98277fcf84f4b64ed60ff49d48f52c1f08487e9fe555eb3d0b1b840774f
Tx public key: b14a5c97a40d2a30e5b75e840ecb089f60b79248275fd06aebb69bee360abe6b
Timestamp: 1705878040 Timestamp [UCT]: 2024-01-21 23:00:40 Age [y:d:h:m:s]: 01:148:08:04:49
Block: 940446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367049 RingCT/type: yes/0
Extra: 01b14a5c97a40d2a30e5b75e840ecb089f60b79248275fd06aebb69bee360abe6b02110000000158e72c11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b21282a3055fd43135f507a52c7ddf444d3b6ad92b18aa65157586d157789e5c 0.600000000000 1398584 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": 940456, "vin": [ { "gen": { "height": 940446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b21282a3055fd43135f507a52c7ddf444d3b6ad92b18aa65157586d157789e5c" } } ], "extra": [ 1, 177, 74, 92, 151, 164, 13, 42, 48, 229, 183, 94, 132, 14, 203, 8, 159, 96, 183, 146, 72, 39, 95, 208, 106, 235, 182, 155, 238, 54, 10, 190, 107, 2, 17, 0, 0, 0, 1, 88, 231, 44, 17, 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