Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1c7e267fe13d5c663820791d4f5a1042c2b78e5bb0da4467d23d7102709023d

Tx prefix hash: dd144be46bb7bfab085efb1df59a5f4208988dc30f06dba5221f689d14818880
Tx public key: fa6c9d4c5979a63a97b84e6c2cea4ed53a91d60c375f3c4eca4ffe79ae4779c9
Timestamp: 1734776656 Timestamp [UCT]: 2024-12-21 10:24:16 Age [y:d:h:m:s]: 00:101:14:46:17
Block: 1179973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72374 RingCT/type: yes/0
Extra: 01fa6c9d4c5979a63a97b84e6c2cea4ed53a91d60c375f3c4eca4ffe79ae4779c9021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 335b9a1bdcd1e0adf70556c0722a944c03e3423a181d47e5590e64d404ce8620 0.600000000000 1666376 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": 1179983, "vin": [ { "gen": { "height": 1179973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "335b9a1bdcd1e0adf70556c0722a944c03e3423a181d47e5590e64d404ce8620" } } ], "extra": [ 1, 250, 108, 157, 76, 89, 121, 166, 58, 151, 184, 78, 108, 44, 234, 78, 213, 58, 145, 214, 12, 55, 95, 60, 78, 202, 79, 254, 121, 174, 71, 121, 201, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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