Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cdc890a0926eb867915242a63ea2ad19705806d27de7fa876a6f3f7ce0a1df5

Tx prefix hash: 171877d6a5c34f639b222dd1b1b40a3f00dc444da3f21df68fb569c9826572aa
Tx public key: b8e3a33dd7733917bd74903a861d42fdbe1d7f12e45f24e2146ab986aab1a90a
Timestamp: 1735681466 Timestamp [UCT]: 2024-12-31 21:44:26 Age [y:d:h:m:s]: 00:354:23:06:21
Block: 1187430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251246 RingCT/type: yes/0
Extra: 01b8e3a33dd7733917bd74903a861d42fdbe1d7f12e45f24e2146ab986aab1a90a02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3650c2b25c9d2a2ff79299a551380d52e5b32938be7311921b25c72973c28c0 0.600000000000 1673921 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": 1187440, "vin": [ { "gen": { "height": 1187430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3650c2b25c9d2a2ff79299a551380d52e5b32938be7311921b25c72973c28c0" } } ], "extra": [ 1, 184, 227, 163, 61, 215, 115, 57, 23, 189, 116, 144, 58, 134, 29, 66, 253, 190, 29, 127, 18, 228, 95, 36, 226, 20, 106, 185, 134, 170, 177, 169, 10, 2, 17, 0, 0, 0, 11, 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