Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44873e004bf7d48c8cb098e0ad7c16dc463af2b640a9cdb0789c70855b1b53fb

Tx prefix hash: 7708c23a3e407db1372e7b76e1e206e37cadc5eb88a0229e3427b5b1346c15fe
Tx public key: 48522b50ee19185cfd8126d7980ac8430b367e61b78456221d33a94d8303f4c4
Timestamp: 1734220288 Timestamp [UCT]: 2024-12-14 23:51:28 Age [y:d:h:m:s]: 00:138:20:39:27
Block: 1175357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99027 RingCT/type: yes/0
Extra: 0148522b50ee19185cfd8126d7980ac8430b367e61b78456221d33a94d8303f4c402110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8be3cca9ce1f8e76f2fcaa76ea74f5cbf666a208b4a82b5cda79ae4561893a61 0.600000000000 1661628 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": 1175367, "vin": [ { "gen": { "height": 1175357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8be3cca9ce1f8e76f2fcaa76ea74f5cbf666a208b4a82b5cda79ae4561893a61" } } ], "extra": [ 1, 72, 82, 43, 80, 238, 25, 24, 92, 253, 129, 38, 215, 152, 10, 200, 67, 11, 54, 126, 97, 183, 132, 86, 34, 29, 51, 169, 77, 131, 3, 244, 196, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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