Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 943bb0ab00b5328a03665a34f2be396abe51eaa737f2fed63010aa3957ef766c

Tx prefix hash: e4659054f4a3537f5f8feb5541ee9750c08e0f2eb926191247ef4217df20c03e
Tx public key: a4b57cb0bbaea8e3e4836684d34586c998b4060d056e95a6a211a074d8a69ae9
Timestamp: 1747352703 Timestamp [UCT]: 2025-05-15 23:45:03 Age [y:d:h:m:s]: 00:232:14:00:43
Block: 1283781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164007 RingCT/type: yes/0
Extra: 01a4b57cb0bbaea8e3e4836684d34586c998b4060d056e95a6a211a074d8a69ae90211000000089f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770687a9cb355478ceb94f4dd7ca77cd05f8dd27fca92f4bc8f97eff6864aeb2 0.600000000000 1771200 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": 1283791, "vin": [ { "gen": { "height": 1283781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770687a9cb355478ceb94f4dd7ca77cd05f8dd27fca92f4bc8f97eff6864aeb2" } } ], "extra": [ 1, 164, 181, 124, 176, 187, 174, 168, 227, 228, 131, 102, 132, 211, 69, 134, 201, 152, 180, 6, 13, 5, 110, 149, 166, 162, 17, 160, 116, 216, 166, 154, 233, 2, 17, 0, 0, 0, 8, 159, 159, 230, 140, 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