Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 068fefa6e3af13eeaa38ce7f3f52969599b14ac1adeca1398df57f7d520c9d1a

Tx prefix hash: 4444702199b34244128edcdd06b91fb2447e443f29fadb85d02ac7eb7afbdcab
Tx public key: dc8c873f48e45e3d761a45e6df46c503ee251058dffcc4c79fac9f9e1728274e
Timestamp: 1729708974 Timestamp [UCT]: 2024-10-23 18:42:54 Age [y:d:h:m:s]: 00:141:03:53:49
Block: 1138016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100692 RingCT/type: yes/0
Extra: 01dc8c873f48e45e3d761a45e6df46c503ee251058dffcc4c79fac9f9e1728274e02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea790009479a55e6cfb5582b690508b21df62d48ed3fb9e18f85cdd1fd7dcf14 0.600000000000 1621615 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": 1138026, "vin": [ { "gen": { "height": 1138016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea790009479a55e6cfb5582b690508b21df62d48ed3fb9e18f85cdd1fd7dcf14" } } ], "extra": [ 1, 220, 140, 135, 63, 72, 228, 94, 61, 118, 26, 69, 230, 223, 70, 197, 3, 238, 37, 16, 88, 223, 252, 196, 199, 159, 172, 159, 158, 23, 40, 39, 78, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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