Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f344f68e061b96f38c35bf090b3538b6c5ed7cd7abaa086e1161c429241575d

Tx prefix hash: af402f515d8dfc36dd389f7f2e6f260da6998db53619b629b1ec0720d8dfa02e
Tx public key: 2561adeb2cf3ee6e2468f72b1a8ea3880167a9592d427aa9d4bbab58a7844935
Timestamp: 1715048136 Timestamp [UCT]: 2024-05-07 02:15:36 Age [y:d:h:m:s]: 00:292:02:38:09
Block: 1016511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208755 RingCT/type: yes/0
Extra: 012561adeb2cf3ee6e2468f72b1a8ea3880167a9592d427aa9d4bbab58a78449350211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 587240d11f5ba80901e6e8a1e62c4fbbe6ce12a355bf95a24c1421d3e548911f 0.600000000000 1480112 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": 1016521, "vin": [ { "gen": { "height": 1016511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "587240d11f5ba80901e6e8a1e62c4fbbe6ce12a355bf95a24c1421d3e548911f" } } ], "extra": [ 1, 37, 97, 173, 235, 44, 243, 238, 110, 36, 104, 247, 43, 26, 142, 163, 136, 1, 103, 169, 89, 45, 66, 122, 169, 212, 187, 171, 88, 167, 132, 73, 53, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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