Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1e9da3bda88b87652c5eec978521c9df353453460736e6eea2f3530e16e48f4

Tx prefix hash: ec107410380c1bea9b68b4342ddbd8a553eadd49c25307286f1d55d5b0a018b6
Tx public key: 79811546f4ee4dac75e4039b1ad1f884d9f5bb553db7db5a5920c09abf187df9
Timestamp: 1648004100 Timestamp [UCT]: 2022-03-23 02:55:00 Age [y:d:h:m:s]: 02:355:20:52:19
Block: 464381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 773647 RingCT/type: yes/0
Extra: 0179811546f4ee4dac75e4039b1ad1f884d9f5bb553db7db5a5920c09abf187df9021100000013bf7ee4e7000000000000000000

1 output(s) for total of 17.754695606000 dcy

stealth address amount amount idx
00: 4121d3d1e92d4351e31f1cc6237c1107353222d775169a586e65c6567b49f73e 17.754695606000 882254 of 0

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": 464391, "vin": [ { "gen": { "height": 464381 } } ], "vout": [ { "amount": 17754695606, "target": { "key": "4121d3d1e92d4351e31f1cc6237c1107353222d775169a586e65c6567b49f73e" } } ], "extra": [ 1, 121, 129, 21, 70, 244, 238, 77, 172, 117, 228, 3, 155, 26, 209, 248, 132, 217, 245, 187, 85, 61, 183, 219, 90, 89, 32, 192, 154, 191, 24, 125, 249, 2, 17, 0, 0, 0, 19, 191, 126, 228, 231, 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