Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad6c67e6b53afad740034eac953b84e375201ad81a1810e9029471d4645759a

Tx prefix hash: a71ceef929a0707623dc2df7bd8d6fe1a5fbd6fc872a7cd7dd15f171977aa672
Tx public key: 125bf52b64d4c533a35c08bb48ea3baeb1e52afb21eceb1a8b57a83319bca13f
Timestamp: 1704910654 Timestamp [UCT]: 2024-01-10 18:17:34 Age [y:d:h:m:s]: 01:163:08:40:32
Block: 932439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377718 RingCT/type: yes/0
Extra: 01125bf52b64d4c533a35c08bb48ea3baeb1e52afb21eceb1a8b57a83319bca13f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 621fca7d1fbe353a4f01eca081e84bef42acaf18361076899e5875fc8c328d17 0.600000000000 1390375 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": 932449, "vin": [ { "gen": { "height": 932439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "621fca7d1fbe353a4f01eca081e84bef42acaf18361076899e5875fc8c328d17" } } ], "extra": [ 1, 18, 91, 245, 43, 100, 212, 197, 51, 163, 92, 8, 187, 72, 234, 59, 174, 177, 229, 42, 251, 33, 236, 235, 26, 139, 87, 168, 51, 25, 188, 161, 63, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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