Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea3ef87bc06f6e4317b5cf50b3e3efe7993e5f5390e2a0fa5cea694335c87196

Tx prefix hash: 5545f09cbfe45e4800100cdec07f84806f1a3003d7121da503c79680248e3ccc
Tx public key: 58e58621693f8e0a5a3c51c3755ec7b2c7bc77aee2109ed61ce88171875d2451
Timestamp: 1725273834 Timestamp [UCT]: 2024-09-02 10:43:54 Age [y:d:h:m:s]: 01:065:08:31:26
Block: 1101278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305131 RingCT/type: yes/0
Extra: 0158e58621693f8e0a5a3c51c3755ec7b2c7bc77aee2109ed61ce88171875d2451021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de547a8f82b5c4f5fd805be3676ae5147262d7e8ef799c4582f95b6f519a95c6 0.600000000000 1577265 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": 1101288, "vin": [ { "gen": { "height": 1101278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de547a8f82b5c4f5fd805be3676ae5147262d7e8ef799c4582f95b6f519a95c6" } } ], "extra": [ 1, 88, 229, 134, 33, 105, 63, 142, 10, 90, 60, 81, 195, 117, 94, 199, 178, 199, 188, 119, 174, 226, 16, 158, 214, 28, 232, 129, 113, 135, 93, 36, 81, 2, 17, 0, 0, 0, 3, 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