Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb49be353ebfac4a2b3a577f831ee73e0af25cc518d6086a20dfd12c1e39850f

Tx prefix hash: 9ea643e6ff2893812a97011fab4efab53edbafe87f1ab112f4b9622bae43d24c
Tx public key: a6c6c4547b76503fd8632661b7192983f50173792696269bc7cdbd3244d5a019
Timestamp: 1688793274 Timestamp [UCT]: 2023-07-08 05:14:34 Age [y:d:h:m:s]: 02:125:03:39:59
Block: 799102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609154 RingCT/type: yes/0
Extra: 01a6c6c4547b76503fd8632661b7192983f50173792696269bc7cdbd3244d5a019021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.381158378000 dcy

stealth address amount amount idx
00: 0d20c4da62fe42d1ab99c06bc8941475c952d0c2145ea482d9a3d84f4f778e48 1.381158378000 1250081 of 0

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": 799112, "vin": [ { "gen": { "height": 799102 } } ], "vout": [ { "amount": 1381158378, "target": { "key": "0d20c4da62fe42d1ab99c06bc8941475c952d0c2145ea482d9a3d84f4f778e48" } } ], "extra": [ 1, 166, 198, 196, 84, 123, 118, 80, 63, 216, 99, 38, 97, 183, 25, 41, 131, 245, 1, 115, 121, 38, 150, 38, 155, 199, 205, 189, 50, 68, 213, 160, 25, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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