Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84bed2b3fbbbc4d7a1ee2563c8766675c1d6a37bec636a83465987cc47362e1

Tx prefix hash: 459b4b1692493da0bdbbe558af282ed9d8464ee1337c1f5e3b7dfe0da2029e60
Tx public key: 3bb3505fcf265ec8cde2b869ad23c591a4b4cf97e4dc89f51443437a938d16a9
Timestamp: 1735942161 Timestamp [UCT]: 2025-01-03 22:09:21 Age [y:d:h:m:s]: 00:321:01:42:48
Block: 1189603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226964 RingCT/type: yes/0
Extra: 013bb3505fcf265ec8cde2b869ad23c591a4b4cf97e4dc89f51443437a938d16a90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff3b767e847bb14513778b0c4a4b58efd29a3318d8bf752ab31e088a1e662730 0.600000000000 1676114 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": 1189613, "vin": [ { "gen": { "height": 1189603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff3b767e847bb14513778b0c4a4b58efd29a3318d8bf752ab31e088a1e662730" } } ], "extra": [ 1, 59, 179, 80, 95, 207, 38, 94, 200, 205, 226, 184, 105, 173, 35, 197, 145, 164, 180, 207, 151, 228, 220, 137, 245, 20, 67, 67, 122, 147, 141, 22, 169, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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