Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8f1947b155b03e6ffd4fe0428e8eae7041f3d144f51026b7914b11f925706a1

Tx prefix hash: 6cc1b0bd03acd97ce9ebde9540fb5bd19951f0a3ad91dac795470a2d80ca19a2
Tx public key: 2761c6ecee34a6838f4cfe3c148d63f6fd8c054742e0671e6e55ecbd9a72d589
Timestamp: 1737250544 Timestamp [UCT]: 2025-01-19 01:35:44 Age [y:d:h:m:s]: 00:057:11:13:46
Block: 1200390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40893 RingCT/type: yes/0
Extra: 012761c6ecee34a6838f4cfe3c148d63f6fd8c054742e0671e6e55ecbd9a72d589021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f348b560dd8702a6db134c49217aafba61d5fe53de40bea1cbb47c458fd7f07e 0.600000000000 1687033 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": 1200400, "vin": [ { "gen": { "height": 1200390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f348b560dd8702a6db134c49217aafba61d5fe53de40bea1cbb47c458fd7f07e" } } ], "extra": [ 1, 39, 97, 198, 236, 238, 52, 166, 131, 143, 76, 254, 60, 20, 141, 99, 246, 253, 140, 5, 71, 66, 224, 103, 30, 110, 85, 236, 189, 154, 114, 213, 137, 2, 17, 0, 0, 0, 5, 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