Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed81d804c7afc0074892ba73802ed1b206593c947669f716e4c2b2d9f6be9cd6

Tx prefix hash: 4157150e657f6a26fb81593c75cd9061aec7b4f353af4f0454d1a41deca04d0d
Tx public key: 08cd8ddf8ca38d24117cdf8dd8d65ea2663f1e83ed2c0142559622f45b177dca
Timestamp: 1733592324 Timestamp [UCT]: 2024-12-07 17:25:24 Age [y:d:h:m:s]: 00:130:19:19:39
Block: 1170146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93277 RingCT/type: yes/0
Extra: 0108cd8ddf8ca38d24117cdf8dd8d65ea2663f1e83ed2c0142559622f45b177dca021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db0671b7cabbf853d2e70740767847ae1d0cbfe3a3cb6210f0741e0b2e2328f1 0.600000000000 1655875 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": 1170156, "vin": [ { "gen": { "height": 1170146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db0671b7cabbf853d2e70740767847ae1d0cbfe3a3cb6210f0741e0b2e2328f1" } } ], "extra": [ 1, 8, 205, 141, 223, 140, 163, 141, 36, 17, 124, 223, 141, 216, 214, 94, 162, 102, 63, 30, 131, 237, 44, 1, 66, 85, 150, 34, 244, 91, 23, 125, 202, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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