Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47d3e84d3a78dc61022ac799ca108dff04dcf51a26fba6da5e7b6a7bfdd51598

Tx prefix hash: ad9525d6c8432e546bc52c9c3d33389e50e8c3eace69ccdc965468e23ff63174
Tx public key: 453f0fa2f38ab08b7be4cd9274204b0eacb0a5189d9cee7cba379e15de04323a
Timestamp: 1721375031 Timestamp [UCT]: 2024-07-19 07:43:51 Age [y:d:h:m:s]: 00:252:09:07:45
Block: 1068970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180276 RingCT/type: yes/0
Extra: 01453f0fa2f38ab08b7be4cd9274204b0eacb0a5189d9cee7cba379e15de04323a02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08fe7aab763304f6f93cb425c9549d88b43ea12941a00e7ee4483d68a1af493e 0.600000000000 1540209 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": 1068980, "vin": [ { "gen": { "height": 1068970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08fe7aab763304f6f93cb425c9549d88b43ea12941a00e7ee4483d68a1af493e" } } ], "extra": [ 1, 69, 63, 15, 162, 243, 138, 176, 139, 123, 228, 205, 146, 116, 32, 75, 14, 172, 176, 165, 24, 157, 156, 238, 124, 186, 55, 158, 21, 222, 4, 50, 58, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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