Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 005a9898e980df26cb1e82b09edca830ed101be2ddbac4ea147475794b4c4f44

Tx prefix hash: d6b80060d8d0b05bc94dcce2c4434de53b8f119cc32268dff2e07331c4461faf
Tx public key: 49d722f9d4891a67e7a076c26733c2bf0fe90ddd6442a7d37427e15ecbbf08db
Timestamp: 1705755121 Timestamp [UCT]: 2024-01-20 12:52:01 Age [y:d:h:m:s]: 01:036:18:28:42
Block: 939422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287352 RingCT/type: yes/0
Extra: 0149d722f9d4891a67e7a076c26733c2bf0fe90ddd6442a7d37427e15ecbbf08db0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f856a2ded9807b5c7b8d60cc7f1a5f2f38ca0b253bbc1f15623151143206dbb8 0.600000000000 1397530 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": 939432, "vin": [ { "gen": { "height": 939422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f856a2ded9807b5c7b8d60cc7f1a5f2f38ca0b253bbc1f15623151143206dbb8" } } ], "extra": [ 1, 73, 215, 34, 249, 212, 137, 26, 103, 231, 160, 118, 194, 103, 51, 194, 191, 15, 233, 13, 221, 100, 66, 167, 211, 116, 39, 225, 94, 203, 191, 8, 219, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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