Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f31e4f87f6cd52a05172010a0420954a2a1ee2d37ff6fcd44ac7b94760a17f3

Tx prefix hash: 2c086a3a3a6c8db2cdd4e78c351b4b8236322f66336669d1ad2aa45220724932
Tx public key: 29b69723a2eaddf2eb92221ef7b6e1346aaaa9895ffbda8c059621438c90ca0c
Timestamp: 1728627710 Timestamp [UCT]: 2024-10-11 06:21:50 Age [y:d:h:m:s]: 00:044:07:38:19
Block: 1129084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31651 RingCT/type: yes/0
Extra: 0129b69723a2eaddf2eb92221ef7b6e1346aaaa9895ffbda8c059621438c90ca0c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f8cf947305621c8f7bed8a9660e275fd97d2a40fd292b800e75142eec815a02 0.600000000000 1611907 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": 1129094, "vin": [ { "gen": { "height": 1129084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f8cf947305621c8f7bed8a9660e275fd97d2a40fd292b800e75142eec815a02" } } ], "extra": [ 1, 41, 182, 151, 35, 162, 234, 221, 242, 235, 146, 34, 30, 247, 182, 225, 52, 106, 170, 169, 137, 95, 251, 218, 140, 5, 150, 33, 67, 140, 144, 202, 12, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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