Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86bb0ddbf68b67bd5116249167eab3e863ec841244a3dd3bf452516923e7702c

Tx prefix hash: f2f37c02cc179898b3903a1ef3453e0c0d96a53cf31fecdb5e47492ecb79f625
Tx public key: a64b45497c2ac0415b9b64a1400ef2d5e15c4b5d77da64d80cbe6ff83900bfd7
Timestamp: 1695689495 Timestamp [UCT]: 2023-09-26 00:51:35 Age [y:d:h:m:s]: 01:171:22:29:41
Block: 856209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383965 RingCT/type: yes/0
Extra: 01a64b45497c2ac0415b9b64a1400ef2d5e15c4b5d77da64d80cbe6ff83900bfd7021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.893355265000 dcy

stealth address amount amount idx
00: 3fa71761a3c1f77e9647fb59a88755e779c2a2b74f17d15d282812e5ad0672d8 0.893355265000 1310271 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": 856219, "vin": [ { "gen": { "height": 856209 } } ], "vout": [ { "amount": 893355265, "target": { "key": "3fa71761a3c1f77e9647fb59a88755e779c2a2b74f17d15d282812e5ad0672d8" } } ], "extra": [ 1, 166, 75, 69, 73, 124, 42, 192, 65, 91, 155, 100, 161, 64, 14, 242, 213, 225, 92, 75, 93, 119, 218, 100, 216, 12, 190, 111, 248, 57, 0, 191, 215, 2, 17, 0, 0, 0, 3, 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