Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a554ebd6f7050aa42b124b23f3e1b849e792960d9012593a0519c398e316a1a0

Tx prefix hash: 5640e7d7b663630d9f3801a7a4e5fab40137c8633af6dc911600ed7ef12f7bc4
Tx public key: b82fb095f5eb884432af5a4525c83c308b1d8328350b1a8135358c7abb5fa4a0
Timestamp: 1755861165 Timestamp [UCT]: 2025-08-22 11:12:45 Age [y:d:h:m:s]: 00:040:07:48:05
Block: 1351942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28681 RingCT/type: yes/0
Extra: 01b82fb095f5eb884432af5a4525c83c308b1d8328350b1a8135358c7abb5fa4a00211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c98de2c57413e02436f44e129aa65590b969401bde86a0d3f21c42f2d4c32803 0.600000000000 1839903 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": 1351952, "vin": [ { "gen": { "height": 1351942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c98de2c57413e02436f44e129aa65590b969401bde86a0d3f21c42f2d4c32803" } } ], "extra": [ 1, 184, 47, 176, 149, 245, 235, 136, 68, 50, 175, 90, 69, 37, 200, 60, 48, 139, 29, 131, 40, 53, 11, 26, 129, 53, 53, 140, 122, 187, 95, 164, 160, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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