Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d5bc511b3819844b2417abb1cae318f4dc719b3a1cef21279631c0694448325

Tx prefix hash: ea2e0c33ceb1e6fc090834b293275ede466e9e776ada8e278c5a294e10a5d6c8
Tx public key: f909caf87e9d30dd6a8f318076d0d7eff52e595edbf967ab7d5fe0f04a24a150
Timestamp: 1724713684 Timestamp [UCT]: 2024-08-26 23:08:04 Age [y:d:h:m:s]: 01:073:12:00:54
Block: 1096625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310975 RingCT/type: yes/0
Extra: 01f909caf87e9d30dd6a8f318076d0d7eff52e595edbf967ab7d5fe0f04a24a150021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17d0da5e4c78178e6bf7fa185a9ab4d13b885ba4001a9fd17868fea909d2103c 0.600000000000 1571816 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": 1096635, "vin": [ { "gen": { "height": 1096625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d0da5e4c78178e6bf7fa185a9ab4d13b885ba4001a9fd17868fea909d2103c" } } ], "extra": [ 1, 249, 9, 202, 248, 126, 157, 48, 221, 106, 143, 49, 128, 118, 208, 215, 239, 245, 46, 89, 94, 219, 249, 103, 171, 125, 95, 224, 240, 74, 36, 161, 80, 2, 17, 0, 0, 0, 1, 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