Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04238606dad92adb0e8725c55a944ac523bd8ff79d20f090fb29b517469548c8

Tx prefix hash: c3bbb41618899340d7c289aaed69310abe74a9118309cc200feb57e5e5df27cc
Tx public key: 283eac89c3671c7593246c0d3b484f3e26da9fce2c57db5c5e63a35821b2e947
Timestamp: 1703573365 Timestamp [UCT]: 2023-12-26 06:49:25 Age [y:d:h:m:s]: 00:342:13:55:51
Block: 921373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245297 RingCT/type: yes/0
Extra: 01283eac89c3671c7593246c0d3b484f3e26da9fce2c57db5c5e63a35821b2e94702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c27952fc8d8852e6d9cf1392d5308cb57cc4a4a89bc2f84875f6ce1a5a4c53db 0.600000000000 1379059 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": 921383, "vin": [ { "gen": { "height": 921373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c27952fc8d8852e6d9cf1392d5308cb57cc4a4a89bc2f84875f6ce1a5a4c53db" } } ], "extra": [ 1, 40, 62, 172, 137, 195, 103, 28, 117, 147, 36, 108, 13, 59, 72, 79, 62, 38, 218, 159, 206, 44, 87, 219, 92, 94, 99, 163, 88, 33, 178, 233, 71, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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