Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05832cdd96a7fa71d035d1b7d59f68d691b1aa2795b9372c02ff79ba3183326d

Tx prefix hash: 0c5f3e27ea2e59d0bd4deaab34985747ddb67becc059a2eacd979e4a29d28961
Tx public key: f372004300fbab7b11380bab6a07122614ad1240bb7e2a0069c6192d84f2fb79
Timestamp: 1723860358 Timestamp [UCT]: 2024-08-17 02:05:58 Age [y:d:h:m:s]: 00:231:12:13:20
Block: 1089564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165326 RingCT/type: yes/0
Extra: 01f372004300fbab7b11380bab6a07122614ad1240bb7e2a0069c6192d84f2fb79021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13c043945e2f39fb1caa8dd6cb5f025afe5862e650903070b1d8d14022f9c0fb 0.600000000000 1564187 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": 1089574, "vin": [ { "gen": { "height": 1089564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13c043945e2f39fb1caa8dd6cb5f025afe5862e650903070b1d8d14022f9c0fb" } } ], "extra": [ 1, 243, 114, 0, 67, 0, 251, 171, 123, 17, 56, 11, 171, 106, 7, 18, 38, 20, 173, 18, 64, 187, 126, 42, 0, 105, 198, 25, 45, 132, 242, 251, 121, 2, 17, 0, 0, 0, 2, 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