Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc34ef2e3032dbbe286e1d71ed876da6f1bcd7a00cf9e399cf87d19a7f730d5a

Tx prefix hash: 8b0601f5f19d5d7ca949a4d6afd89096a1bbadb6d2ec1d558978d5e30c66d08d
Tx public key: e8d87253771df8a5690455449cc5a0f0d71de852e7f14ce7b993db4b8db5ae28
Timestamp: 1695607913 Timestamp [UCT]: 2023-09-25 02:11:53 Age [y:d:h:m:s]: 01:194:22:18:12
Block: 855534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400370 RingCT/type: yes/0
Extra: 01e8d87253771df8a5690455449cc5a0f0d71de852e7f14ce7b993db4b8db5ae280211000000034b8f5122000000000000000000

1 output(s) for total of 0.897997787000 dcy

stealth address amount amount idx
00: e3abed7f9743971a13bd931ee62486609010377c463be32f12bfe085f3b4248b 0.897997787000 1309558 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": 855544, "vin": [ { "gen": { "height": 855534 } } ], "vout": [ { "amount": 897997787, "target": { "key": "e3abed7f9743971a13bd931ee62486609010377c463be32f12bfe085f3b4248b" } } ], "extra": [ 1, 232, 216, 114, 83, 119, 29, 248, 165, 105, 4, 85, 68, 156, 197, 160, 240, 215, 29, 232, 82, 231, 241, 76, 231, 185, 147, 219, 75, 141, 181, 174, 40, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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